Add Elasticflow MCP server to catalog#1079
Conversation
Elasticflow is an AI-native workspace for business — a remote MCP server (Streamable HTTP + OAuth 2.1) exposing 46 tools across workspaces, tables, documents, files, and interfaces. - Name: io.github.stacklok/elasticflow - Remote URL: https://mcp.elasticflow.app/mcp - Tier: Community - License: MIT
JAORMX
left a comment
JAORMX
left a comment
There was a problem hiding this comment.
Thanks for the submission — this is the most complete of the recent remote-server PRs: https://mcp.elasticflow.app/mcp is a real OAuth 2.1 MCP endpoint (unauthenticated initialize returns 401, and .well-known/oauth-protected-resource resolves), the namespace/location/tier/_meta key are all correct, it's MIT, and you actually committed an icon.svg. A few changes before it can go in:
Please fix:
- Overview format. The
overviewmust start with a## Elasticflowheading followed by ~3–5 sentences. The current value is marketing copy (opens with "One workspace where…" and includes a bulleted feature list, no heading). Please reformat to## Elasticflow\n\n+ a concise 3–5 sentence description. - Add the
repositoryfield. The top-levelrepositoryis missing. Add:"repository": { "url": "https://github.com/elasticflowapp/elasticflow-mcp", "source": "github" }
- Icon
srchost. It points toraw.githubusercontent.com/stacklok/toolhive-catalog/..., but every existing entry referencesstacklok/toolhive-registry(https://raw.githubusercontent.com/stacklok/toolhive-registry/main/registries/toolhive/servers/elasticflow/icon.svg). Please match that host so it's consistent with the rest of the catalog (the committedicon.svgitself is fine). If the canonical host has intentionally changed, a maintainer can confirm. - Remove
metadata.last_updated. That field is auto-populated by CI and shouldn't be set by hand.
Minor / confirm:
- OAuth looks correct via discovery (
.well-known/oauth-protected-resource), so no explicitoauth_configis needed — consistent with other OAuth remotes likeatlassian-remote.tagsalready includeoauth. 👍 - One note: being listed in the upstream Official MCP Registry isn't part of our inclusion criteria — we evaluate each entry independently against our criteria. Not a blocker, just clarifying.
Happy to re-review once the overview, repository, icon host, and metadata are addressed.
|
Thanks for the submission, and for building on MCP! The registry requires entries to be open source with publicly accessible source code (criteria). The linked repo currently contains only packaging metadata (README, LICENSE, icon, With no updates since the review on Jun 3, we're going to close this for now. If the server implementation becomes publicly available, we'd be happy to revisit. Thanks for your patience. |
2 participants
Summary
Adds Elasticflow to the ToolHive catalog as a remote MCP server (Streamable HTTP + OAuth 2.1).
io.github.stacklok/elasticflowWhat Elasticflow is
Elasticflow is an AI-native workspace for business — a single place where AI agents and the team work together on structured data, documents, files, and live dashboards. The MCP server exposes that workspace so any MCP-compatible client (Claude, ChatGPT, Cursor, Cline, Copilot Studio, Amazon Q, Gemini, and others) can read business data, produce durable artifacts, and publish results the whole organization sees.
The server is already listed in the Official MCP Registry as
app.elasticflow/mcp(v1.0.0).Files added
registries/toolhive/servers/elasticflow/server.json— catalog entry following the upstream MCPServerJSONschema with ToolHive_metaextensions (tier, status, tags, tools, custom_metadata)registries/toolhive/servers/elasticflow/icon.svg— logoChecklist
server.jsonuses the upstream MCP schema (2025-12-11)_meta.io.modelcontextprotocol.registry/publisher-provided.io.github.stacklokextension key matchesremotes[0].urlserver.jsonLinks